Skip to main content

This is a new service – your feedback will help us to improve it.

East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1164

reference
650-tree-1
name
1164
tree-preservation-order

undefined

650-tpo-1
uprn
address-text
point
POINT (-1.011055 50.865769)
geometry
MULTIPOLYGON (((-1.010999 50.865762,-1.011001 50.865774,-1.011009 50.865784,-1.011021 50.865792,-1.011037 50.865797,-1.011055 50.865799,-1.011072 50.865797,-1.011088 50.865792,-1.011101 50.865784,-1.011109 50.865775,-1.011112 50.865763,-1.011110 50.865752,-1.011102 50.865742,-1.011089 50.865734,-1.011074 50.865729,-1.011056 50.865727,-1.011039 50.865729,-1.011023 50.865734,-1.011010 50.865741,-1.011002 50.865751,-1.010999 50.865762)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL